Repository navigation
Explain how scripts, templates and presets get to each machine - #214
Merged
Merged
Conversation
A first-time tester couldn't tell how to get Reaper scripts and track templates working across machines: linking, Bring over, Keep Files in Sync and Choose what syncs were spread over four screens with nothing saying which comes first. A compact "Scripts, templates and presets" Notice line now sits in Get Up To Speed, Set up, This machine and Settings > Sync. It names the next step (link, then turn on syncing) with its button, or turns green once both are done. "How it works" opens the ways in order, each ticked when done here, plus what is never copied. Buttons reach the Link dialog and other tabs through a small ShellContext. Bring over's "link first" line gets a Link a machine button; Set up's intro and tour step 5 say to link first. Decision #122; docs/what-syncs.md gains a "Getting it working" section. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Se1kixnHqBR6qsjjYcSA9
…-2xcsej # Conflicts: # app/src/App.tsx # docs/decisions.md
3 of 5 tasks
joshuadav86
added a commit
that referenced
this pull request
Nov 6, 2026
Version bump and CHANGELOG entry for the files guide (#214, decision #122). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013Se1kixnHqBR6qsjjYcSA9
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Joshua · project thread
No issue; Joshua asked in the project thread (a first-time tester couldn't tell how to get Reaper scripts, track templates and the rest working across machines).
What changed
app/src/FilesGuide.tsx) in Get Up To Speed (this machine), Set up, This machine and Settings > Sync. The line names the next step with its button (Link a machine…, then Set up sync…), or turns green once linked and syncing. How it works opens the ways in order, each ticked when it's done here:It ends with what's never copied: plug-ins, Reaper extensions and sample libraries; reaper.ini and audio/MIDI settings stay per machine.
app/src/shell.ts: a smallShellContextso these buttons can open the Link dialog, This machine's Sync & backup, Settings or Get Up To Speed without passing props through every screen.App.tsxgains two wrapper lines and the context value (left unindented to keep the diff small next to PR Ask a few setup questions on the first run #213).docs/what-syncs.mdgains a short "Getting it working" section.How it was tested
npm run build(tsc + vite)/mnt/project-files/screenshots/files-guide/(scriptshoot.cjsthere)Checklist
docs/decisions.md(App layout pass: one style for notices, cards and buttons on every screen #122)Generated by Claude Code